Tamper evident removable media storing executable code

ABSTRACT

A mobile wireless device operable to install code on a removable medium, in which the device is programmed to calculate and store a digest of this code into a persistent non-removable store inside the device. When the removable medium is plugged back, and when the code is invoked, the device recalculates a digest from the code it wants to load from the removable medium and compares it with the one stored inside the persistent non-removable store. If they do not match, the code has been tampered with and therefore cannot be trusted by the device. The digest is accessible only by components in the Trusted Computing Base so is itself secure. The digest may be a hash or other unique and representative value.

FIELD OF THE INVENTION

This invention relates to an apparatus providing tamper evidence for executable code stored on removable media. This apparatus forms an element in a platform security architecture.

DESCRIPTION OF THE PRIOR ART

Platform security covers the philosophy, architecture and implementation of platform defence mechanisms against malicious or badly written code. These defence mechanisms prevent such code from causing harm. Malicious code generally has two components: a payload mechanism that does the damage and a propagation mechanism to help it spread. They are usually classified as follows:

-   -   Trojan horse: poses as a legitimate application that appears         benign and attractive to the user.     -   Worm: can replicate and spread without further manual action by         their perpetrators or users.     -   Virus: Infiltrates legitimate programs and alters or destroys         data.

Security threats encompass (a) a potential breach of confidentiality, integrity or availability of services or data in the value chain and integrity of services and (b) compromise of service function. Threats are classified into the following categories:

-   -   1. Threats to confidentiality and integrity of data. Examples:         Get user's password; corrupt files.     -   2. Threats to confidentiality and integrity of services.         Examples: Use bandwidth from phone network subscriber without         paying for it; repudiate transaction with network service         provider.     -   3. Threats to availability of service (also called denial of         service). Examples: Prevent the user from sending a text         message; prevent the user from accepting a telephone call.

Hence, mobile wireless devices offer very considerable challenges to the designer of a platform security architecture. One critical aspect of this challenge is that mobile wireless devices will regularly install programs on removable storage devices. The main motivation is to provide extra storage that the wireless device user can change, based on which set of programs he/she wishes to use. A well-known example is the usage of floppy diskettes or memory cards in personal computer environments. The removable storage device might, in principle, be tampered with in some way when not plugged into the mobile wireless device and the programs stored on the device would hence lose their integrity. It is vital that, in all circumstances, a wireless device is confident in the integrity of executable code, including when a removable storage device is to be re-inserted (e.g. that no malicious alterations to override security features have been made and no viruses introduced etc).

To date, there have however been no efficient proposals for ensuring the integrity of executable code which has been transferred off from a mobile wireless device and is being returned to the original device.

SUMMARY OF THE PRESENT INVENTION

In a first aspect of the present invention, there is a mobile wireless device operable to install native executable code on a removable medium, in which the device is programmed to calculate and store a digest (a digest is a value generated from the full content of the code using an algorithm guaranteeing that the same value cannot be regenerate if the content has changed) of this code into a persistent non-removable store inside the device. Native code is composed of instructions directly executed by a CPU on a device.

When the removable medium is plugged back, and when the executable is invoked, the device recalculates a digest from the code it wants to load from the removable medium and compares it with the one stored inside the persistent non-removable store. If they do not match, the executable has been tampered with and therefore cannot be trusted by the device. The digest is accessible only by components in the Trusted Computing Base (see later) so is itself secure. The digest may be a hash or other unique and representative value that can be recomputed from the entire executable.

This approach differs from conventional watermarking, in which a hash is derived from a media file and then inserted back into the file, modifying it imperceptibly.

In one implementation, the digest as well as the executable's ‘capability’ are securely stored on the device. A ‘capability’ can be thought of as an access token that corresponds to a permission to undertake a sensitive action. (The purpose of the capability model is to control access to sensitive system resources.) At load time, the loader verifies the hash before loading. If the verification fails, the executable will not be loaded. If the executable is unknown (no associated digest), the executable is loaded with no capability (i.e no access rights to sensitive resources) and no identity (no access rights to data that is private to an identified operating system process). If the verification succeeds, then the executable is loaded and the stored capability assigned to the newly loaded code.

The present invention allows users to share memory cards and other forms of removable medium between devices without restriction. It also allows each user to keep the privileges he/she has granted to applications stored on these cards independent from the medium and other users' choices.

DETAILED DESCRIPTION

The present invention will be described with reference to the security architecture of the Symbian OS object oriented operating system, designed for single user wireless devices. The Symbian OS operating system has been developed for mobile wireless devices by Symbian Ltd, of London United Kingdom. defences. In a similar fashion, it employs simple and staggered layers of security above and beyond the installation perimeter. The key threats that the model is trying to address are those that are linked with unauthorised access to user data and to system services, in particular the phone stack. The phone stack is especially important in the context of a smart phone because it will be controlling a permanent data connection to the phone network. There are two key design drivers lying behind the model:

-   -   Firewall protection of key system resources through the use of         capability-based access control.     -   Data partitioning which creates a protected part of the file         system which standard software is not able to access.

The main concept of the capability model described below is to control what a process can do rather than what a user can do. This approach is quite different to well-known operating systems as Windows NT and Unix. The main reasons are:

-   -   The very nature of Symbian OS is to be mono-user.     -   Symbian OS provides services through independent server         processes. They always run and are not attached to a user         session. As long as power is supplied, Symbian OS is always on         even if no user is logged on.     -   Symbian OS is aimed to be used in devices used by a large public         with no technology knowledge. When installing software, the user         may not have the skills to decide what permissions to grant to         an application. Furthermore, with always-connected devices, the         consequences of a wrong or malevolent decision may impact a         domain much larger than the device itself.         1 Trusted Computing Platform         1.1 Trusted Computing Base

A trusted computing base (TCB) is a basic architectural requirement for robust platform security. The trusted computing base consists of a number of architectural elements that cannot be subverted and that guarantee the integrity of the device. It is important to keep this base as small as possible and to apply the principle of least privilege to ensure system servers and applications do not have to be given privileges they do not need to function. On closed devices, the TCB consists of the kernel, loader and file server; on open devices the software installer is also required. All these processes are system-wide trusted and have therefore full access to the device. This trusted core would run with a “root” capability not available to other platform code (see section 2.1).

There is one other important element to maintain the integrity of the trusted computing base that is outside the scope of the present invention, namely the hardware. In particular, with devices that hold trusted computing base functionality in flash ROM, it is necessary to provide a secure boot loader to ensure that it is not possible to subvert the trusted computing base with a malicious ROM image.

1.2 Trusted Computing Environment

Beyond the core, other system components would be granted restricted orthogonal system capability and would constitute the Trusted Computing Environment (TCE); they would include system servers such as socket, phone and window servers. For instance the window server would not be granted the capability of phone stack access and the phone server would not be granted the capability of direct access to keyboard events. It is strongly recommended to give as few system capabilities as possible to a software component to limit potential damage by any misuse of these privileges.

The TCB ensures the integrity of the full system as each element of the TCE ensures the integrity of one service. The TCE cannot exist without a TCB but the TCB can exist by itself to guarantee a safe “sand box” for each process.

2 Process Capabilities

A capability can be thought of as an access token that corresponds to a permission to undertake a sensitive action. The purpose of the capability model is to control access to sensitive system resources. The most important resource that requires access control is the kernel executive itself and a system capability (see section 2.1) is required by a client to access certain functionality through the kernel API. All other resources reside in user-side servers accessed via IPC [Inter Process Communication]. A small set of basic capabilities would be defined to police specific client actions on the servers. For example, possession of a make calls capability would allow a client to use the phone server. It would be the responsibility of the corresponding server to police client access to the resources that the capability represents. Capabilities would also be associated with each library (DLL) and program (EXE) and combined by the loader at run time to produce net process capabilities that would be held by the kernel. For open devices, third party software would be assigned capabilities either during software installation based on the certificate used to sign their installation packages or post software installation by the user,. The policing of capabilities would be managed between the loader, the kernel and affected servers but would be kernel-mediated through the IPC mechanism.

The key features of the process capability model are:

-   -   It is primarily focused around system servers and client-server         IPC interactions between these entities.     -   Capabilities are associated with processes and not threads.         Threads in the same process share the same address space and         memory access permissions. This means that any data being used         by one thread can be read and modified by all other threads in         the same process.     -   The policing of the capabilities is managed by the loader and         kernel and through capability policing at the target servers.         The kernel IPC mechanism is involved in the latter.     -   When the code is not running, capabilities are stored inside of         libraries and programs. Capabilities stored in libraries and         programs are not modifiable, as they would be stored during         installation in a location that is only accessible by the         Trusted Computing Base. * Not all servers would have to handle         client capabilities. Servers would be responsible for         interpreting capabilities as they wish.     -   The only cryptography involved in this scheme might be at the         software installation stage where certificates would be checked         off against a suitable root certificate.         2.1 System capabilities: Protecting the Integrity of the Device         Root. “Full Access to all Files—Can Modify Capabilities         Associated with Executables

“Root” capability—Used by the Trusted Computing Base only, it gives full access to all files in the device.

System Capabilities

Some system servers require some specific access to the Trusted Computing Base.

Because of the object-oriented implementation of Symbian OS, the kind of resources required by a system server is most of the time exclusive to it. Therefore, one system server would be granted some system capability that would be orthogonal to those required by another. For instance, the window server would be granted access to keyboard and pen events issued by the kernel but it would not have permission to access the phone stack. In the same way, the phone server would be granted access to the phone stack but would not have permission to collect events from the kernel.

As examples, we can name: WriteSystemData Allows modification of configuration system data CommDD Grants access to all communication and Ethernet card device drivers. DiskAdmin Can perform administration task on the disk (reformat, rename a drive, . . . ). 2.2 User-Exposed Capabilities: Mapping Real-World Permissions

The process of generating capabilities can be difficult. One has first to identify those accesses that require policing and then to map those requirements into something that is meaningful for a user. In addition, more capabilities means greater complexity and complexity is widely recognised as being the chief enemy of security. A solution based on capabilities should therefore seek to minimise the overall number deployed. The following capabilities map fairly broadly onto the main threats which are unauthorised access to system services (eg. the phone stack) and preserving the confidentiality/integrity of user data.

PhoneNetwork. “Can access phone network services and potentially spend user money”

-   -   “Make telephone calls”     -   “Send short text messages”.

WriteUserData. “Can read and modify users private information”

-   -   “Add a contact”.     -   “Delete an appointment”.

ReadUserData. “Can read users private information”

-   -   “Access contacts data”.     -   “Access agenda data”.

LocalNetwork. “Can access local network”

-   -   “Send Bluetooth messages”.     -   “Establish an IR connection”     -   “Establish an USB connection”

Location. “Can access the current location of the device”

-   -   “Locate the device on a map”     -   “Display closest restaurants and cinema”

Root and system capabilities are mandatory; if not granted to an executable, the user of the device cannot decide to do it. Their strict control ensures the integrity of the Trusted Computing Platform. However the way servers check user-exposed capabilities or interpret them may be fully flexible and even user-discretionary.

2.3 Assigning Capabilities to a Process

The association of a run-time capability with a process involves the loader. In essence, it transforms the static capability settings associated with individual libraries and programs into a run-time capability that the kernel holds and can be queried through a kernel user library API. The loader applies the following rules:

-   -   Rule 1. When creating a process from a program, the loader         assigns the same set of capabilities as its program's.     -   Rule 2. When loading a library within an executable, the library         capability set must be greater than or equal to the capability         set of the loading executable. If not true, the library is not         loaded into the executable.     -   Rule 3. An executable can load a library with higher         capabilities, but does not gain capabilities by doing so.     -   Rule 4. The loader refuses to load any executable not in the         data caged part of the file system reserved to the TCB.

It has to be noted that:

-   -   Libraries' capabilities are checked at load time only. Beyond         that, all code contained in libraries is run freely and is         assigned the same capability set as the program it runs into         when initiating some IPC calls.     -   For ROM images with execution in place, the ROM build tool         resolves all symbols doing the same task as the loader at         runtime. Therefore the ROM build tool must enforce the same         rules as the loader when building a ROM image.

These rules

-   -   Prevent malware from being loaded in sensitive processes, for         example, a plug-in in a system server     -   Encourage encapsulation of sensitive code inside processes with         no possible bypass

The examples below show how these rules are applied in the cases of statically and dynamically loaded libraries respectively.

2.3.1 Examples for Linked DLLs

The program P.EXE is linked to the library L1.DLL.

The library L1.DLL is linked to the library L0.DLL.

Case 1:

-   -   P.EXE holds Cap1 & Cap2     -   L1.DLL holds Cap1 & Cap2 & Cap3     -   L0.DLL holds Cap1 & Cap2.     -   Process P cannot be created, the loader fails it because L1.DLL         cannot load L0.DLL. Since L0.DLL does not have a capability set         greater than or equal to L1.DLL, Rule 2 applies.

Case 2:

-   -   P.EXE holds Cap1 & Cap2     -   L1.DLL holds Cap1 & Cap2 & Cap3     -   L0.DLL holds Cap1 & Cap2 & Cap3 & Cap4     -   Process P is created, the loader succeeds it and the new process         is assigned Cap1 & Cap2. The capability of the new process is         determined by applying Rule 1; L1.DLL cannot acquire the Cap4         capability held by L0.DLL, and P1.EXE cannot acquire the Cap3         capability held by L1.DLL as defined by Rule 3.         2.3.2 Examples for Dynamically Loaded DLLs

The program P.EXE dynamically loads the library L1.DLL. P The library L1.DLL then dynamically loads the library L0.DLL.

Case 1:

-   -   P.EXE holds Cap1 & Cap2     -   L1.DLL holds Cap1 & Cap2 & Cap3     -   L0.DLL holds Cap1 & Cap2     -   Process P is successfully created and assigned Cap1 & Cap2.     -   When P requests the loader to load L1.DLL & L0.DLL, the loader         succeeds it because P can load L1.DLL and L0.DLL. Rule 2 does         apply here the loading executable being the process P not the         library L1.DLL: the IPC load request that the loader processes         is sent by the process P. The fact that the call is within         L1.DLL is here irrelevant. Rule 1 & 3 apply as before and P does         not acquire Cap3 by loading L1.DLL

Case 2:

-   -   P.EXE holds Cap1 & Cap2     -   L1.DLL holds Cap1 & Cap2& Cap3     -   L0.DLL holds Cap1 & Cap2 & Cap4     -   Process P is successfully created and assigned Cap1 & Cap2. When         P requests the loader to load L1.DLL & L0.DLL, the loader         succeeds it because P can load L1.DLL and L0.DLL. Once again,         Rule 2 does apply with P as the loading executable rather than         L1.DLL, while Rule 3 ensures P acquires neither Cap3 nor Cap4.         2.4 How to Combine the Flexibility of Removable Media with         Platform Security         2.4.1 Today         2.4.1.1 Device Integrity

Today, files stored on removable media are completely unprotected. They are fully accessible and can be modified. When a removable medium is plugged back in the device, no checks are performed to ensure the integrity of the system. Risks associated with this fact may be seen as low because possession of the medium is needed for subversion. However a malicious user may install malware and damage not her device but use it as a weapon against network operators, for instance. Today without platform security, the only protection is to implement a loader that refuses to load code from removable media. However in the long term, more memory space will be required to store more applications and this strategy will prevent users buying software for their device and potentially might discourage them to buy open platforms if they could not take advantage of it.

2.4.1.2 Data Confidentiality

Threats on data confidentiality ate real but limited only to data contained on the stolen removable medium. Most of the threats can be already prevented without the support of platform security:

-   -   1. Hardware control access to the medium         -   Even off the device, the medium is password-protected; for             instance Secure MMC, PIN-protected SIM, etc.     -   2. File encryption         -   If a user is concerned about the security of some sensitive             data and wants to store it on a removable medium, he/she may             encrypt it.     -   3. File system encryption         -   File system encryption may be provided at disk device driver             level.             2.4.2 Proposed Invention

The proposed invention aims not only to prevent current threats but also to keep the interoperability and code distribution uses of removable media.

No platform security architecture can prevent the modification of removable media when off the wireless device. Even with a password-protected removable medium, an authorised user can alter it. Therefore, the best Platform Security can provide is a tamper evidence mechanism for known executables and a secure execution of unknown code

2.4.2.1 Software Installer

At install time, when an application package has to be stored on a removable medium:

-   -   Step 1. The software installer verifies that executables to be         installed on removable media have got a correct secure         identifier (SID) and have not impersonated another legitimate         executable to access to its private data.     -   Step 2 The software installer assigns some system and user         capabilities to executables included in the application package.     -   Step 3. The software installer hashes the executables.     -   Step 4. The software installer stores all capabilities and the         hash (i.e. digest) in a TCB-restricted area of a permanent file         system (e.g. that cannot be removed).

At de-install time, the software installer removes the executables from the removable medium if present and destroys the associated file created at installation step 4

For preformatted removable media (files already installed), a lighter version of the application package must be provided too in order to let the Software Installer perform steps 1 to 3. The present invention does not specify any apparatus for detecting new applications on pre-formatted removable media; a possible option may be to detect the presence of new applications at the time of insertion of the removable medium in the wireless device and to consider the removal of a pre-formatted removable medium as the de-installation of applications it contains.

2.4.2.2 Loader

At load time, the loader identifies an executable to load from a removable medium. It looks at the corresponding HASH file: the hash in a TCB-restricted area of a permanent file system (e.g. that cannot be removed).

-   -   If it exists, it hashes the executable and compares both hashes.         -   If identical, the loader assigns system and user             capabilities extracted from the HASH file to the executable             and performs the standard loading process.         -   If not, the loader returns an error.     -   If no corresponding HASH file exists, the loader assigns no         system and user capability to the executable and performs the         standard loading process. It also assigns the secure identifier         (SID) (the SID (secure identifier) of a process is a way of         uniquely identifying a piece of code capable of running on the         OS and is stored in the related executable) to ‘unknown’ to         prevent impersonation of a legitimate process. As no capability         and no SID are granted to unknown code, this one cannot         compromise the integrity of the Trusted Computing Platform.

The hashing process must be independent of the removable medium. What has to be achieved is to authenticate a piece of code, not the removable medium it comes from. The preferred implementation uses SHA-1 as it is reasonably secure and fast for use in a wireless device.

2.4.3 Use Cases

2.4.3.1 Actors

1. U an user.

2. P1, P2 two wireless devices owned by U.

3. C1, C2 two removable media owned by U.

4. APP an application with only one executable.

5. Loader

b 6. SWInstall, the software installer

7. ETEL the process controlling access to the phone network.

2.4.3.2 Assumptions

1. APP is delivered as a signed application package APP.sis with PhoneNetwork capability.

2. C: is the internal drive

3. D: is a removable medium drive.

4. C1 contains APP.sis under root. APP.sis is the installation package of APP.

2.4.3.3 Use Case 1—U Installs APP on P1.

1. U plugs C1 into P1.

2. U uses P1.

3. U asks SWInstall to install D:APP.sis on drive D:\.

4. SWInstall verifies the signing certificate. {E1}

5. SWInstall extracts APP.app.

6. SWInstall removes system and user capabilities from the executable and copies them to a to c:\<directory accessible to TCB only>\APP.cap.

7. SWInstall hashes APP.app and stores it in c:\<directory accessible to TCB only>\APP.cap.

8. SWInstall copies APP.app to D:

9. SWInstall completes the installation.

E1-Invalid signature

1. End of the use case.

2.4.3.4 Use Case 2—U copies C1 into C2 off line and uses C2 with P1.

1. U copies C1 into C2 offline.

2. U plugs C2 in P1.

3. U uses P1.

4. U asks Loader to start APP.

5. Loader finds APP.app in D:\

6. Loader opens c:\<directory accessible to TCB only>\APP.cap.

7. Loader verifies hashes successfully. {E2}

8. Loader extracts system and user capabilities from APP.cap

9. Loader loads APP.app and assigns capabilities to APP.app.

10. U asks APP to dial a number.

11. APP asks ETEL to dial a number

12. ETEL successfully checks APP has got PhoneNetwork.

13. ETEL dials the number.

14. U uses the phone connection.

E2—Hashes mismatch

1. Loader does not load APP and returns Binary Hash Mismatch error.

2. U cannot use APP.

2.4.3.5 Use Case 3—U uses C1 with P2

1. U plugs C1 in P2.

2. U uses P2.

3. U asks Loader to start APP.

4. Loader finds APP.app in D:

5. Loader does not find c:\<directory accessible to TCB only>\APP.cap.

6. Loader loads APP.app and assigns no user and system capabilities to APP.app

7. U asks APP to dial a number.

8. APP asks ETEL to dial a number

9. ETEL detects APP has not got PhoneNetwork.

10. ETEL asks U if she wants to make the call.

11. U accepts. {E1}

12. ETEL dials the number.

13. U uses the phone connection.

E1-U does not accepts

1. ETEL does not dial the number.

2. APP displays an error to U.

2.4.3.6 Use Case 4—U Installs APP on P2 and Demotes APP's PhoneNetwork

1. U plugs C1 in P2.

2. U uses P2.

3. U successfully installs APP on P2 D:\(refer to Use case 1)

4. U asks SWInstall to remove PhoneNetwork from APP's capabilities.

5. SWInstall modifies c:\<directory accessible to TCB only>\APP.cap and reset user capabilities in the file.

6. U asks Loader to start APP.

7. Loader finds APP.app in D:\

8. Loader opens c:\<directory accessible to TCB only>\APP.cap.

9. Loader verifies hashes successfully. {E2}

10. Loader extracts capabilities from APP.cap

11. Loader loads APP.app and assigns capabilities to APP.app.

12. U asks APP to dial a number.

13. APP asks ETEL to dial a number

14. ETEL detects APP has not got PhoneNetwork.

15. ETEL asks U if she wants to make the call. 16. U accepts. {E1}

17. ETEL dials the number.

18. U uses the phone connection.

19. U plugs C1 on P1.

20. U asks APP to dial a number.

21. APP asks ETEL to dial a number

22. ETEL successfully checks APP has got PhoneNetwork.

23. ETEL dials the number.

24. U uses the phone connection.

E1—U does not accepts

1. ETEL does not dial the number.

2. APP displays an error to U.

E2—Hashes mismatch

1. Loader does not load APP and returns Binary Hash Mismatch error.

2. U cannot use APP.

2.4.3.7 Use Case 5—U Uninstalls APP from P2 with C2

1. U plugs C2 in P2.

2. U uses P2.

3. U asks SWInstall to uninstall APP.

4. SWInstall deletes c:\<directory accessible to TCB only>\APP.cap.

5. SWInstall asks U to confirm deletion on D:.

6. U confirms. {E1}

7. SWInstall deletes APP.app from D:.

8. U cannot use C2 on P1 or P2 to start APP.

E2—U does not confirm

1. SWInstall does not delete APP.app on D.

2. U can still use C2 with P1 to start APP.

2.4.3.8 Use Case 6—U Hackes APP.app to Add Some System Capability.

1. U modifies APP.app system capabilities off line on C1.

2. U plugs C1 in P1.

3. U uses P1.

4. U asks Loader to start APP.

5. Loader finds APP.app in D:

6. Loader opens c:\<directory accessible to TCB only>\APP.cap.

7. Loader does not verify the hash successfully.

8. Loader does not load APP and returns Binary Hash Mismatch error.

9. U cannot use APP.

2.4.3.9 Conclusion

These use cases show that even with Platform Security, the flexibility provided by removable media is kept:

-   -   To share cards between devices with different user capability         settings.     -   To duplicate cards and use the copies without restriction.     -   To securely execute code from removable media. 

1. A mobile wireless device operable to install native executable code on a removable medium, in which the device is programmed to calculate and store a digest of this code into a persistent non-removable store inside the device.
 2. The device of claim 1 programmed such that, when the removable medium is plugged back into the device, and the code is invoked, the device recalculates a digest from the code it wants to load from the removable medium and compares it with the one stored inside the persistent non-removable store, preventing use if the calculated digest and the stored digest differ.
 3. The device of claim 1 in which the stored digest is accessible only by components in a trusted computing base.
 4. The device of claim 1 in which the digest as well as the executable's capability are securely stored on the device.
 5. The device of claim 1 in which, if no verification is possible because the executable is unknown, the executable is loaded without any capability and identity.
 6. The device of claim 2 in which if the verification fails, then the executable is not loaded.
 7. The device of claim 1 in which if the verification succeeds then the executable is loaded and assigned capabilities securely stored on the device.
 8. A method of using executable code stored on a removable medium, comprising the steps of: (a) calculating and storing a first digest of this code into a persistent non-removable store inside a mobile wireless device (b) transferring the executable code onto a removable medium coupled to the device; (c) de-coupling the removable medium; (d) re-coupling the removable medium; (e) calculating a new digest from the code stored on the removable medium; (f) comparing the new digest with the first digest; (g) preventing use of the code if the new digest and the first digest differ.
 9. The method of claim 8 in which the first digest is accessible only by components in a trusted computing base.
 10. The method of claim 8 in which the first digest as well as the executable's capability are securely stored on the device.
 11. The method of claim 8 in which, if no verification is possible because the executable is unknown, the executable is loaded without any capability and identity.
 12. The method of claim 8 in which if the verification fails, then the executable is not loaded.
 13. The method of claim 8 in which if the verification succeeds then the executable is loaded and assigned capabilities securely stored on the device. 